chore(examples): Updating vendor examples #3966
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
jfermi
reviewed
Aug 14, 2024
| 4. Run `docker compose run tracetest-run`. | ||
| 5. Follow the links in the output to view the test results. | ||
|
|
||
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. |
There was a problem hiding this comment.
Suggested change
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. | |
| Follow the sections below for a detailed breakdown of what the example you just ran did and how it works. |
jfermi
reviewed
Aug 14, 2024
| Increasing the duration to a more reasonable `500ms` will make the test pass. | ||
|
|
||
|  | ||
| ## Running the tests |
There was a problem hiding this comment.
Suggested change
| ## Running the tests | |
| ## Running the Tests |
jfermi
reviewed
Aug 14, 2024
| 4. Run `docker compose run tracetest-run`. | ||
| 5. Follow the links in the output to view the test results. | ||
|
|
||
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. |
There was a problem hiding this comment.
Suggested change
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. | |
| Follow the sections below for a detailed breakdown of what the example you just ran did and how it works. |
jfermi
reviewed
Aug 14, 2024
|  | ||
|
|
||
| Increasing the duration to a more reasonable `500ms` will make the test pass. | ||
| ## Running the tests |
There was a problem hiding this comment.
Suggested change
| ## Running the tests | |
| ## Running the Tests |
jfermi
reviewed
Aug 14, 2024
| 4. Run `docker compose run tracetest-run`. | ||
| 5. Follow the links in the output to view the test results. | ||
|
|
||
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. |
There was a problem hiding this comment.
Suggested change
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. | |
| Follow the sections below for a detailed breakdown of what the example you just ran did and how it works. |
jfermi
reviewed
Aug 14, 2024
| ``` | ||
|
|
||
| This will start your Tracetest instance on `http://localhost:11633/`. | ||
| ## Running the tests |
There was a problem hiding this comment.
Suggested change
| ## Running the tests | |
| ## Running the Tests |
jfermi
reviewed
Aug 14, 2024
| 4. Run `docker compose run tracetest-run`. | ||
| 5. Follow the links in the output to view the test results. | ||
|
|
||
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. |
There was a problem hiding this comment.
Suggested change
| Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works. | |
| Follow the sections below for a detailed breakdown of what the example you just ran did and how it works. |
jfermi
reviewed
Aug 14, 2024
|
|
||
| ## Run both the OpenTelemetry Demo app and Tracetest | ||
| ## Running the tests |
There was a problem hiding this comment.
Suggested change
| ## Running the tests | |
| ## Running the Tests |
adnanrahic
approved these changes
Aug 15, 2024
| The `docker-compose.yaml` file, `collector.config.yaml`, `tracetest-provision.yaml`, and `tracetest-config.yaml` in the `tracetest` directory are for setting up Tracetest and the OpenTelemetry Collector. | ||
|
|
||
| The `tracetest` directory is self-contained and will run all the prerequisites for enabling OpenTelemetry traces and trace-based testing with Tracetest, as well as routing all traces the OpenTelemetry Demo generates to Datadog. | ||
|
|
||
| ### Docker Compose Network | ||
|
|
||
| All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces. |
There was a problem hiding this comment.
Suggested change
| All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces. | |
| All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest-agent:4317` in the `collector.config.yaml` will map to the `tracetest-agent` service, where port `4317` is the port where Tracetest Agent accepts traces. |
| @@ -40,8 +66,6 @@ The `docker-compose.yaml` file and `.env` file in the root directory are for the | |||
|
|
|||
| The `docker-compose.yaml` file, `collector.config.yaml`, `tracetest-provision.yaml`, and `tracetest-config.yaml` in the `tracetest` directory are for setting up Tracetest and the OpenTelemetry Collector. | |||
|
|
|||
| The `tracetest` directory is self-contained and will run all the prerequisites for enabling OpenTelemetry traces and trace-based testing with Tracetest, as well as routing all traces the OpenTelemetry Demo generates to Dynatrace. | |||
|
|
|||
| ### Docker Compose Network | |||
|
|
|||
| All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces. | |||
There was a problem hiding this comment.
Suggested change
| All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces. | |
| All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest-agent:4317` in the `collector.config.yaml` will map to the `tracetest-agent` service, where port `4317` is the port where Tracetest Agent accepts traces. |
| - test-specs | ||
|
|
||
| ``` | ||
|
|
||
| ### Sending Traces to Tracetest and Dynatrace | ||
|
|
||
| The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Dynatrace in another. |
There was a problem hiding this comment.
Suggested change
| The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Dynatrace in another. | |
| The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest Agent's OTLP endpoint `tracetest-agent:4317` in one pipeline, and to Dynatrace in another. |
| @@ -256,23 +130,22 @@ receivers: | |||
| - targets: ['0.0.0.0:8888'] | |||
|
|
|||
| processors: | |||
| batch: # this configuration is needed to guarantee that the data is sent correctly to Dynatrace | |||
| batch: # this configuration is needed to guarantee that the data is sent correctly to Datadog | |||
There was a problem hiding this comment.
Suggested change
| batch: # this configuration is needed to guarantee that the data is sent correctly to Datadog | |
| batch: # this configuration is needed to guarantee that the data is sent correctly to Dynatrace |
| checkoutEndpoint: otel-checkoutservice:5050 | ||
|
|
||
| ``` | ||
|
|
||
| **How to Send Traces to Tracetest and Lightstep** | ||
|
|
||
| The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Lightstep in another. |
There was a problem hiding this comment.
Suggested change
| The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Lightstep in another. | |
| The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest Agent's OTLP endpoint `tracetest-agent:4317` in one pipeline, and to Lightstep in another. |
| The `docker-compose.yaml` file, `collector.config.yaml`, `tracetest-provision.yaml`, and `tracetest-config.yaml` in the `tracetest` directory are for the setting up Tracetest and the OpenTelemetry Collector. | ||
|
|
||
| The `tracetest` directory is self-contained and will run all the prerequisites for enabling OpenTelemetry traces and trace-based testing with Tracetest, as well as routing all traces the OpenTelemetry Demo generates to New Relic. | ||
|
|
||
| ### Docker Compose Network | ||
|
|
||
| All `services` in the `docker-compose.yaml` are on the same network and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where the port `4317` is the port where Tracetest accepts traces. |
There was a problem hiding this comment.
Suggested change
| All `services` in the `docker-compose.yaml` are on the same network and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where the port `4317` is the port where Tracetest accepts traces. | |
| All `services` in the `docker-compose.yaml` are on the same network and will be reachable by hostname from within other services. E.g. `tracetest-agent:4317` in the `collector.config.yaml` will map to the `tracetest-agent` service, where the port `4317` is the port where Tracetest Agent accepts traces. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR...
Changes
Fixes
Checklist
Loom video
Add your loom video here if your work can be visualized